Search This CD Index Contact Us
Home > Administration > ADAP > getload
| getload
> ### getload Get load measurement lists #### Syntax ####
> getload -f day [-d mmddyy] [-n nn] [-r release] [-v] [-w] [-V] [> ofile] or getload -f hour [-d mmddyy] [-t hh] [-n nn] [-r release] [-v] [-w] [-V] [> ofile]
> #### Description This command retrieves the following screen for the date you specify in the command options: INTUITY AUDIX List Measurements Load Day This command retrieves the following screen for the date and time you specify in the command options: INTUITY AUDIX List Measurements Load Hour No input is required. Retrieved data is written to standard output.
> -f | Screen flag; must be followed by either day or hour.
> day | Retrieves day version of the screen data.
> hour | Retrieves hour version of the screen data.
> -d | Date flag; must be followed by mmddyy. If this flag is omitted, the most recent date's data will be returned.
> mmddyy | Retrieves data for the month, day, and year indicated by mmddyy. For example, if you enter 072201 without subsequently entering the -n option, only the data for July 22, 2001, will be retrieved.
> -t | Time of the day; flag must be followed by hh. If this flag is omitted, the first hour (hour 0) of the specified day or the current hour (if no day is specified) will be returned.
> hh | Retrieves data for the hour (hh) of the day (mmddyy) that you have specified already. For example, if you enter 15 without subsequently entering the -n option, only the data from 3:00 p.m. to 4:00 p.m. will be retrieved.
> -n | Number of records flag; must be followed by nn. If you do not include this flag, only one record (hour or day) will be returned.
> nn | Retrieves the number (nn) of hourly or daily records that you specify. For example, if you want to retrieve hourly data and you enter 15 for hh and then enter 5 for nn, the data for the hours between 3:00 p.m. and 8:00 p.m. (the data beginning at 3:00 and continuing through the next five hours) will be retrieved.
> | The same is true for daily records. If you enter 082201 for mmddyy and then enter 8 for nn, the data from and including August 22, 2001, and continuing through August 29, 2001, will be retrieved.
> | For the INTUITY AUDIX System, you may use the value all to retrieve all records (hour or day) on or after any specified date and time.
> -r | Indicates that the argument following is the name of the release. This argument must be followed by release.
> release | Retrieves data for the specified release of the software.
> -v | Writes transfer statistics to the screen at the end of the transfer.
> | Pressing -v while the command is executing sends the updated transfer status to the screen
> -w | Writes a one-line summary of the exit status of this command into the file, form_req.rc.
> -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > ofile | Specifies the name of the file to which data will be written. The filename must be preceded by the symbol >. If no output file is specified, data is written to the screen.
> #### Errors If the specified date and time is before any valid date and time when communicating with a INTUITY AUDIX System, the retrieval starts at the first date and time with data. If the specified date and time is after a valid date, an error message is returned and the retrieval aborts. #### Output format Output for the getload command when communicating with an INTUITY AUDIX System using the -f day option is formatted as follows, with one record for each day.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | starting date | D | 8
> | ending time | T | 4
> | subscriber threshold list exceptions | N | 5
> | subscriber threshold list space exceptions | N | 5
> | subscriber lower msg space exceptions | N | 5
> | subscriber upper msg space exceptions | N | 5
> | total subscribers over threshold | N | 19
> | deliveries rescheduled | N | 8
> | maximum simultaneous ports | N | 3
> | maximum voice text used | N | 9
> | minimum voice text free space | N | 9
> | port 1 usage in seconds | N | 6
> | port 2 usage in seconds | N | 6
> | port 3 usage in seconds | N | 6
> | port 4 usage in seconds | N | 6
> | port 5 usage in seconds | N | 6
> | port 6 usage in seconds | N | 6
> | port 7 usage in seconds | N | 6
> | port 8 usage in seconds | N | 6
> | port 9 usage in seconds | N | 6
> | port 10 usage in seconds | N | 6
> | port 11 usage in seconds | N | 6
> | port 12 usage in seconds | N | 6
> | port 13 usage in seconds | N | 6
> | port 14 usage in seconds | N | 6
> | port 15 usage in seconds | N | 6
> | port 16 usage in seconds | N | 6
> | port 17 usage in seconds | N | 6
> | port 18 usage in seconds | N | 6
> | port 19 usage in seconds | N | 6
> | port 20 usage in seconds | N | 6
> | port 21 usage in seconds | N | 6
> | port 22 usage in seconds | N | 6
> | port 23 usage in seconds | N | 6
> | port 24 usage in seconds | N | 6
> | port 25 usage in seconds | N | 6
> | port 26 usage in seconds | N | 6
> | port 27 usage in seconds | N | 6
> | port 28 usage in seconds | N | 6
> | port 29 usage in seconds | N | 6
> | port 30 usage in seconds | N | 6
> | port 31 usage in seconds | N | 6
> | port 32 usage in seconds | N | 6
> | port 1 peg count | N | 6
> | port 2 peg count | N | 6
> | port 3 peg count | N | 6
> | port 4 peg count | N | 6
> | port 5 peg count | N | 6
> | port 6 peg count | N | 6
> | port 7 peg count | N | 6
> | port 8 peg count | N | 6
> | port 9 peg count | N | 6
> | port 10 peg count | N | 6
> | port 11 peg count | N | 6
> | port 12 peg count | N | 6
> | port 13 peg count | N | 6
> | port 14 peg count | N | 6
> | port 15 peg count | N | 6
> | port 16 peg count | N | 6
> | port 17 peg count | N | 6
> | port 18 peg count | N | 6
> | port 19 peg count | N | 6
> | port 20 peg count | N | 6
> | port 21 peg count | N | 6
> | port 22 peg count | N | 6
> | port 23 peg count | N | 6
> | port 24 peg count | N | 6
> | port 25 peg count | N | 6
> | port 26 peg count | N | 6
> | port 27 peg count | N | 6
> | port 28 peg count | N | 6
> | port 29 peg count | N | 6
> | port 30 peg count | N | 6
> | port 31 peg count | N | 6
> | port 32 peg count | N | 6
> | port 33 usage in seconds | N | 6
> | port 34 usage in seconds | N | 6
> | port 35 usage in seconds | N | 6
> | port 36 usage in seconds | N | 6
> | port 37 usage in seconds | N | 6
> | port 38 usage in seconds | N | 6
> | port 39 usage in seconds | N | 6
> | port 40 usage in seconds | N | 6
> | port 41 usage in seconds | N | 6
> | port 42 usage in seconds | N | 6
> | port 43 usage in seconds | N | 6
> | port 44 usage in seconds | N | 6
> | port 45 usage in seconds | N | 6
> | port 46 usage in seconds | N | 6
> | port 47 usage in seconds | N | 6
> | port 48 usage in seconds | N | 6
> | port 49 usage in seconds | N | 6
> | port 50 usage in seconds | N | 6
> | port 51 usage in seconds | N | 6
> | port 52 usage in seconds | N | 6
> | port 53 usage in seconds | N | 6
> | port 54 usage in seconds | N | 6
> | port 55 usage in seconds | N | 6
> | port 56 usage in seconds | N | 6
> | port 57 usage in seconds | N | 6
> | port 58 usage in seconds | N | 6
> | port 59 usage in seconds | N | 6
> | port 60 usage in seconds | N | 6
> | port 61 usage in seconds | N | 6
> | port 62 usage in seconds | N | 6
> | port 63 usage in seconds | N | 6
> | port 64 usage in seconds | N | 6
> | port 33 peg count | N | 6
> | port 34 peg count | N | 6
> | port 35 peg count | N | 6
> | port 36 peg count | N | 6
> | port 37 peg count | N | 6
> | port 38 peg count | N | 6
> | port 39 peg count | N | 6
> | port 40 peg count | N | 6
> | port 41 peg count | N | 6
> | port 42 peg count | N | 6
> | port 43 peg count | N | 6
> | port 44 peg count | N | 6
> | port 45 peg count | N | 6
> | port 46 peg count | N | 6
> | port 47 peg count | N | 6
> | port 48 peg count | N | 6
> | port 49 peg count | N | 6
> | port 50 peg count | N | 6
> | port 51 peg count | N | 6
> | port 52 peg count | N | 6
> | port 53 peg count | N | 6
> | port 54 peg count | N | 6
> | port 55 peg count | N | 6
> | port 56 peg count | N | 6
> | port 57 peg count | N | 6
> | port 58 peg count | N | 6
> | port 59 peg count | N | 6
> | port 60 peg count | N | 6
> | port 61 peg count | N | 6
> | port 62 peg count | N | 6
> | port 63 peg count | N | 6
> | port 64 peg count | N | 6
> | total storage used (hours) | N | 12.1
> | total storage free (hours) | N | 12.1
> | message storage used (hours) | N | 12.1
> | voiced name storage used (hours) | N | 12.1
> | percent remote | N | 2
> | announcement storage used (hours) | N | 12.1
> | maximum simultaneous IMAPI sessions | N | 3
> Output for the getload command when communicating with INTUITY AUDIX System using the -f hour option is formatted asfollows, with one record for each hour.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | starting date | D | 8
> | starting hour | N | 2
> | ending time | T | 4
> | subscriber threshold list exceptions | N | 5
> | subscriber threshold list space exceptions | N | 5
> | subscriber lower msg space exceptions | N | 5
> | subscriber upper msg space exceptions | N | 5
> | total subscribers over threshold | N | 19
> | deliveries rescheduled | N | 8
> | maximum simultaneous ports | N | 3
> | maximum voice text used | N | 9
> | minimum voice text free space | N | 9
> | port 1 usage in seconds | N | 6
> | port 2 usage in seconds | N | 6
> | port 3 usage in seconds | N | 6
> | port 4 usage in seconds | N | 6
> | port 5 usage in seconds | N | 6
> | port 6 usage in seconds | N | 6
> | port 7 usage in seconds | N | 6
> | port 8 usage in seconds | N | 6
> | port 9 usage in seconds | N | 6
> | port 10 usage in seconds | N | 6
> | port 11 usage in seconds | N | 6
> | port 12 usage in seconds | N | 6
> | port 13 usage in seconds | N | 6
> | port 14 usage in seconds | N | 6
> | port 15 usage in seconds | N | 6
> | port 16 usage in seconds | N | 6
> | port 17 usage in seconds | N | 6
> | port 18 usage in seconds | N | 6
> | port 19 usage in seconds | N | 6
> | port 20 usage in seconds | N | 6
> | port 21 usage in seconds | N | 6
> | port 22 usage in seconds | N | 6
> | port 23 usage in seconds | N | 6
> | port 24 usage in seconds | N | 6
> | port 25 usage in seconds | N | 6
> | port 26 usage in seconds | N | 6
> | port 27 usage in seconds | N | 6
> | port 28 usage in seconds | N | 6
> | port 29 usage in seconds | N | 6
> | port 30 usage in seconds | N | 6
> | port 31 usage in seconds | N | 6
> | port 32 usage in seconds | N | 6
> | port 1 peg count | N | 6
> | port 2 peg count | N | 6
> | port 3 peg count | N | 6
> | port 4 peg count | N | 6
> | port 5 peg count | N | 6
> | port 6 peg count | N | 6
> | port 7 peg count | N | 6
> | port 8 peg count | N | 6
> | port 9 peg count | N | 6
> | port 10 peg count | N | 6
> | port 11 peg count | N | 6
> | port 12 peg count | N | 6
> | port 13 peg count | N | 6
> | port 14 peg count | N | 6
> | port 15 peg count | N | 6
> | port 16 peg count | N | 6
> | port 17 peg count | N | 6
> | port 18 peg count | N | 6
> | port 19 peg count | N | 6
> | port 20 peg count | N | 6
> | port 21 peg count | N | 6
> | port 22 peg count | N | 6
> | port 23 peg count | N | 6
> | port 24 peg count | N | 6
> | port 25 peg count | N | 6
> | port 26 peg count | N | 6
> | port 27 peg count | N | 6
> | port 28 peg count | N | 6
> | port 29 peg count | N | 6
> | port 30 peg count | N | 6
> | port 31 peg count | N | 6
> | port 32 peg count | N | 6
> | port 33 usage in seconds | N | 6
> | port 34 usage in seconds | N | 6
> | port 35 usage in seconds | N | 6
> | port 36 usage in seconds | N | 6
> | port 37 usage in seconds | N | 6
> | port 38 usage in seconds | N | 6
> | port 39 usage in seconds | N | 6
> | port 40 usage in seconds | N | 6
> | port 41 usage in seconds | N | 6
> | port 42 usage in seconds | N | 6
> | port 43 usage in seconds | N | 6
> | port 44 usage in seconds | N | 6
> | port 45 usage in seconds | N | 6
> | port 46 usage in seconds | N | 6
> | port 47 usage in seconds | N | 6
> | port 48 usage in seconds | N | 6
> | port 49 usage in seconds | N | 6
> | port 50 usage in seconds | N | 6
> | port 51 usage in seconds | N | 6
> | port 52 usage in seconds | N | 6
> | port 53 usage in seconds | N | 6
> | port 54 usage in seconds | N | 6
> | port 55 usage in seconds | N | 6
> | port 56 usage in seconds | N | 6
> | port 57 usage in seconds | N | 6
> | port 58 usage in seconds | N | 6
> | port 59 usage in seconds | N | 6
> | port 60 usage in seconds | N | 6
> | port 61 usage in seconds | N | 6
> | port 62 usage in seconds | N | 6
> | port 63 usage in seconds | N | 6
> | port 64 usage in seconds | N | 6
> | port 33 peg count | N | 6
> | port 34 peg count | N | 6
> | port 35 peg count | N | 6
> | port 36 peg count | N | 6
> | port 37 peg count | N | 6
> | port 38 peg count | N | 6
> | port 39 peg count | N | 6
> | port 40 peg count | N | 6
> | port 41 peg count | N | 6
> | port 42 peg count | N | 6
> | port 43 peg count | N | 6
> | port 44 peg count | N | 6
> | port 45 peg count | N | 6
> | port 46 peg count | N | 6
> | port 47 peg count | N | 6
> | port 48 peg count | N | 6
> | port 49 peg count | N | 6
> | port 50 peg count | N | 6
> | port 51 peg count | N | 6
> | port 52 peg count | N | 6
> | port 53 peg count | N | 6
> | port 54 peg count | N | 6
> | port 55 peg count | N | 6
> | port 56 peg count | N | 6
> | port 57 peg count | N | 6
> | port 58 peg count | N | 6
> | port 59 peg count | N | 6
> | port 60 peg count | N | 6
> | port 61 peg count | N | 6
> | port 62 peg count | N | 6
> | port 63 peg count | N | 6
> | port 64 peg count | N | 6
> | total storage used (hours) | N | 12.1
> | total storage free (hours) | N | 12.1
> | message storage used (hours) | N | 12.1
> | voiced name storage used (hours) | N | 12.1
> | percent remote | N | 2
> | announcement storage used (hours) | N | 12.1
> | maximum simultaneous IMAPI sessions | N | 3
> ### getlog Get activity log data #### Syntax
> getlog [-a y/n] -e nnnnnnnnnn [-d mmddyy [-t hhmm]] [-s mmddyy [-h hhmm]] [-n nn] [-r release] [-v] [-w] [-V] [> ofile]
> #### Description This command retrieves data for the following screen for starting and ending date, starting and ending time, and extension that you specify: INTUITY AUDIX Display Activity-Log When used with an INTUITY System, this command does not turn on or off the activity log (see getalogp and setalogp). Only the option e is required. By default, all entries for the indicated extension are returned. The screen is updated with any of the options you specify except r, v, w, or n. For INTUITY AUDIX Systems, ADAP updates the specification fields of the Display Activity-Log screen while retrieving the data. The voice mail system retains the values you supply after the retrieval is completed. No input is required. Retrieved data is written to standard output.
> -a | Activity log (activates log capabilities) flag; must be followed by either a y or n.
> -e | Extension flag; must be followed by nnnnnnnnnn. This flag is required for the INTUITY AUDIX System when the -a flag is y.
> nnnnnnnnnn | Retrieves data for the specified extension.
> -d | Starting date flag; must be followed by mmddyy.
> mmddyy | Retrieves data starting at the month, day, and year indicated by mmddyy.
> -t | Starting time flag; must be followed by hhmm. This flag is only available if the -d flag is also used.
> hhmm | Retrieves data starting from the hour and minute of the day that you have specified already by -d mmddyy. Midnight is represented by 0000.
> -s | Ending date flag; must be followed by mmddyy.
> mmddyy | Stops retrieving data at the month, day, and year indicated by mmddyy.
> -h | Ending time flag; must be followed by hhmm. This flag is only available if the -s flag is also used.
> hhmm | Stops retrieving data at the hour and minute of the day that you have specified already by -s mmddyy. Midnight is represented by 0000.
> -n | Record number flag; must be followed by nn.
> nn | Retrieves the number (nn) of records that you specify. If the word all is used, all records that meet the specification criteria will be returned.
> -r | Release flag; must be followed by release.
> release | Retrieves data for the specified release of the software.
> -v | Writes transfer statistics to the screen at the end of the transfer.
> | Pressing -v while the command is executing sends the updated transfer status to the screen.
> -w | Writes a one-line summary of the exit status of this command into the file, form_req.rc.
> -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > ofile | Specifies the name of the file to which data will be written. The filename must be preceded by the symbol >. If no output file is specified, data is written to the screen.
> #### Errors If the activity log was activated then deactivated, only the data prior to the deactivation date/time is available. This is subject to the number of entries that the system activity log holds, as specified on the INTUITY AUDIX Systems Display System-Parameters Activity-Log screen. If no activity log data exists that fits the specified search, no output is written. #### Output format Output for the getlog command when communicating with a INTUITY AUDIX System is formatted as follows, with one record for each log entry.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> 1 | date | D | 8
> 2 | time | T | 4
> 3 | activity | C | 9
> 4 | description | C | 100
> #### Example The following command retrieves the INTUITY AUDIX Display Activity-Log screen data for extension 3101 for November 22, 2001, and writes output to a file named actlog. getlog -e 3101 -d 112201 -s 032201> actlog <RETURN> The following data is written to the file, one line for each activity: `19941122,1822,"log-in","message counts: new=0, unopened=0, old=0" NEWLINE` ### getmaint Get maintenance log data #### Syntax
> getmaint [-d mmddyy [-t hhmm]] [-c event id] [-f search string] [-A application] [-a alarm resolution] [-E errors] [-e events] [-R reporting-resource-type] [-T resource-type [-L location]] [-n nnnn] [-r release] [-v] [-w] [-V] [> ofile]
> #### Description This command retrieves all pages for the date, time, and search information that you specify for the following screens: INTUITY AUDIX Display Events ADAP updates the specification fields of the INTUITY AUDIX Display Maintenance-Log screen while retrieving the data. If you omit the options and their qualifiers then all records from and including the specified date and time are returned. For complete lists of errors and resource types, see the appropriate voice mail system maintenance manual. No input is required. All errors retrieved are written to standard output. Note: The getmaint command requires the craft login for the INTUITY AUDIX System.
> -d | Date flag; must be followed by mmddyy. The default retrieves entries for all dates.
> mmddyy | Retrieves data for the month, day, and year indicated by mmddyy. For example, 072201, retrieves data for July 22, 2001.
> -t | Time of the day flag; must be followed by hhmm. The default retrieves all entries starting at the specified date.
> hhmm | Retrieves errors from the specified hour and minute to the current time. For example, if you enter 1512 at 6:00 p.m. (for retrieval on the same day), the data from 3:12 p.m. to 6:00 p.m.is retrieved.
> -c | Event id flag; must be followed by event id.
> event id | Retrieves errors matching the error code that you specify. See the appropriate voice mail system maintenance manual for a list of event ids.
> -f | Search string flag; must be followed by search string.
> search string | Retrieves errors containing the search string you specify. The maximum string length for INTUITY AUDIX Systems is 78 characters.
> -A | Application flag; must be followed with application.
> application | Retrieves only records logged against this application (module), i.e. VM.
> -a | RES alarm resolution information flag; must be followed by either y or n. The default is y.
> alarm resolution | Retrieves or does not retrieve alarm RES (resolution) information.
> -E | ERR (error) information flag; must be followed by y or n. Default is y.
> errors | Retrieves or does not retrieve ERR (error) information.
> -e | EVN (event) information flag; must be followed by either y or n. The default is y.
> events | Retrieves or does not retrieve EVN (event) information.
> -R | Retrieves records logged by the resource type.
> reporting- resource- type | Retrieves records logged by the resource type (module) that you specify. See the appropriate voice mail system maintenance manual for a list of resource types.
> -T | Resource type flag; must be followed with resource-type.
> resource- type | Retrieves records logged against the resource type that you specify. See the appropriate voice mail system maintenance manual for a list of resource types.
> -L | Location flag; must be followed with location.
> location | Retrieves errors logged against resources at the specified location. The T resource-type argument must also be specified.
> -n | Number of records flag; must be followed by nnnn.If this flag is not specified, retrieves all records meeting specification criteria.
> nnnn | Retrieves the number (nnnn) of records that you specify.
> -r | Release flag; must be followed by release.
> release | Retrieves data for the specified release of the software.
> -v | Writes transfer statistics to the screen at the end of the transfer.
> | Pressing v while the command is executing sends the updated transfer status to the screen.
> -w | Writes a one-line summary of the exit status of this command into the file, form_req.rc.
> -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > ofile | Specifies the name of the output file; filename must be preceded by > . If no output file is specified, data is written to the screen.
> #### Errors If no errors match the specified search, no output is written. #### Output format Output for the getmaint command is formatted as follows.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | problem resource, type | C | 14
> | problem resource, instance | C | 3
> | problem resource, location | C | 11
> | message type | C | 3
> | reporting resource, type | C | 14
> | reporting resource, instance | C | 3
> | reporting resource, source | C | 19
> | application | C | 2
> | event id | C | 14
> | date | D | 8
> | time | T | 4
> | count | C | 3
> | text | C | 78
> #### Example The following command retrieves the INTUITY AUDIX Display Events data from 12:25 p.m. on September 14, 1994, to the hour and minute the command was entered, writes a summary of the transfer statistics to the screen, and writes output to a file named errors. getmaint -d 091494 -t 1225 -v > errors <RETURN> The following data is written to the file: `"SOFTWARE","1","","ERR","MCM","1","3222","VM", "SOFTWARE0602",19940914,1225," 1", "AUX1/2=0/0,109-ALARM-LOG:RAISING MIN ALARM 602 ON SOFTWARE/1" <NEWLINE>` ### getmlist Get machine list #### Syntax
> getmlist [-r release] [-v] [-w] [-V] [> ofile]
> #### Description This command retrieves all pages for the following screen: INTUITY AUDIX List Machines No input is required. Retrieved data is written to standard output.
> -r | Release flag; must be followed by release.
> release | Retrieves data for the specified release of the INTUITY AUDIX.
> -v | Writes transfer statistics to the screen at the end of the transfer.
> | Pressing v while the command is executing sends the updated transfer status to the screen.
> -w | Writes a one-line summary of the exit status of this command into the file, form_req.rc.
> -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > ofile | Specifies the name of the file to which data is written. The filename must be preceded by the symbol >. If no output file is specified, data is written to the screen.
> The following caution applies only to AUDIX systems: If operators on the local maintenance terminal (LMT) and the local administration terminal (LAT) concurrently access the same screen information, output on either terminal could prematurely terminate or reflect other undesirable changes. #### Output format Output for the getmlist command is as follows, one record for each machine.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | machine name | C | 10
> | voice id | C | 3
> | machine type | C | 12
> | callback number | C | 3
> ### getnet Get network load data #### Syntax
> getnet -f day [-d mmddyy] [-n nn] [-r release] [-v] [-w] [-V] [>ofile] or getnet -f hour [-d mmddyy] [-h hh] [-n nn] [-r release] [-v] [-w] [-V] [>ofile]
> #### Description This command retrieves data for the date specified for the following screen: INTUITY AUDIX List Measurements Network-Load Day This command retrieves data for the date and time specified for the following screens: INTUITY AUDIX List Measurements Network-Load Hour No input is required. Retrieved data is written to standard output.
> -f | Screen flag; must be followed by either day or hour.
> day | Retrieves the day version of the screen.
> hour | Retrieves the hour version of the screen.
> -d | Date flag; must be followed by mmddyy.
> mmddyy | Retrieves data for the month, day, and year indicated by mmddyy. For example, if you enter 012201 without subsequently entering the n option, only the data for January 22, 2001, will be retrieved.
> -h | Time of day flag; must be followed by hh.
> hh | Retrieves data for the hour of the day (hh) that you specify. For example, if you enter 15 without subsequently entering the n option, only the data from 3:00 p.m. to 4:00 p.m. will be retrieved.
> -n | Number of records flag; must be followed by nn. Omitting this flag retrieves one record.
> nn | Retrieves the number (nn) of hourly or daily records that you specify. For example, if you want to retrieve hourly data and you enter 15 for hh and then enter 5 for nn, the data for the hours between 3:00 p.m. and 8:00 p.m. (the data beginning at 3:00 and continuing through the next five hours) will be retrieved.
> | The same is true for daily records. If you enter 092294 for mmddyy and then enter 8 for nn, the data from and including September 22, 1994, and continuing through September 29, 1994, will be retrieved.
> -r | Release flag; must be followed by release.
> release | Retrieves data for the specified release of the software.
> -v | Writes transfer statistics to the screen at the end of the transfer. Pressing v while the command is executing sends the updated transfer status to the screen.
> -w | Writes a one-line summary of the exit status of this command into the file, form_req.rc.
> -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > ofile | Specifies the name of the file to which data will be written. The filename must be preceded by the symbol >. If no output file is specified, data is written to the screen.
> #### Output format Output for the getnet command when communicating with an INTUITY AUDIX System using the -f day option is formatted as follows, one record for each day.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | starting date | D | 8
> | ending time | T | 4
> | total msg transmission threshold exceptions | N | 7
> | total msg transmission limit exceptions | N | 7
> | remote deliveries rescheduled | N | 8
> | maximum simultaneous channels | N | 3
> | total incoming calls unanswered | N | 5
> | total remote undeliverable messages | N | 8
> | network channel 1 type | C | 6
> | network channel 1 usage, incoming | N | 7
> | network channel 1 usage, outgoing | N | 7
> | network channel 1 usage, total | N | 7
> | network channel 1 peg count, incoming | N | 6
> | network channel 1 peg count, outgoing | N | 6
> | network channel 1 peg count, total | N | 6
> | network channel 2 type | C | 6
> | network channel 2 usage, incoming | N | 7
> | network channel 2 usage, outgoing | N | 7
> | network channel 2 usage, total | N | 7
> | network channel 2 peg count, incoming | N | 6
> | network channel 2 peg count, outgoing | N | 6
> | network channel 2 peg count, total | N | 6
> | network channel 3 type | C | 6
> | network channel 3 usage, incoming | N | 7
> | network channel 3 usage, outgoing | N | 7
> | network channel 3 usage, total | N | 7
> | network channel 3 peg count, incoming | N | 6
> | network channel 3 peg count, outgoing | N | 6
> | network channel 3 peg count, total | N | 6
> | network channel 4 type | C | 6
> | network channel 4 usage, incoming | N | 7
> | network channel 4 usage, outgoing | N | 7
> | network channel 4 usage, total | N | 7
> | network channel 4 peg count, incoming | N | 6
> | network channel 4 peg count, outgoing | N | 6
> | network channel 4 peg count, total | N | 6
> | network channel 5 type | C | 6
> | network channel 5 usage, incoming | N | 7
> | network channel 5 usage, outgoing | N | 7
> | network channel 5 usage, total | N | 7
> | network channel 5 peg count, incoming | N | 6
> | network channel 5 peg count, outgoing | N | 6
> | network channel 5 peg count, total | N | 6
> | network channel 6 type | C | 6
> | network channel 6 usage, incoming | N | 7
> | network channel 6 usage, outgoing | N | 7
> | network channel 6 usage, total | N | 7
> | network channel 6 peg count, incoming | N | 6
> | network channel 6 peg count, outgoing | N | 6
> | network channel 6 peg count, total | N | 6
> | network channel 7 type | C | 6
> | network channel 7 usage, incoming | N | 7
> | network channel 7 usage, outgoing | N | 7
> | network channel 7 usage, total | N | 7
> | network channel 7 peg count, incoming | N | 6
> | network channel 7 peg count, outgoing | N | 6
> | network channel 7 peg count, total | N | 6
> | network channel 8 type | C | 6
> | network channel 8 usage, incoming | N | 7
> | network channel 8 usage, outgoing | N | 7
> | network channel 8 usage, total | N | 7
> | network channel 8 peg count, incoming | N | 6
> | network channel 8 peg count, outgoing | N | 6
> | network channel 8 peg count, total | N | 6
> | network channel 9 type | C | 6
> | network channel 9 usage, incoming | N | 7
> | network channel 9 usage, outgoing | N | 7
> | network channel 9 usage, total | N | 7
> | network channel 9 peg count, incoming | N | 6
> | network channel 9 peg count, outgoing | N | 6
> | network channel 9 peg count, total | N | 6
> | network channel 10 type | C | 6
> | network channel 10 usage, incoming | N | 7
> | network channel 10 usage, outgoing | N | 7
> | network channel 10 usage, total | N | 7
> | network channel 10 peg count, incoming | N | 6
> | network channel 10 peg count, outgoing | N | 6
> | network channel 10 peg count, total | N | 6
> | network channel 11 type | C | 6
> | network channel 11 usage, incoming | N | 7
> | network channel 11 usage, outgoing | N | 7
> | network channel 11 usage, total | N | 7
> | network channel 11 peg count, incoming | N | 6
> | network channel 11 peg count, outgoing | N | 6
> | network channel 11 peg count, total | N | 6
> | network channel 12 type | C | 6
> | network channel 12 usage, incoming | N | 7
> | network channel 12 usage, outgoing | N | 7
> | network channel 12 usage, total | N | 7
> | network channel 12 peg count, incoming | N | 6
> | network channel 12 peg count, outgoing | N | 6
> | network channel 12 peg count, total | N | 6
> Output for the getnet command when communicating with an INTUITY AUDIX System using the -f hour option is formatted as follows, with one record for each hour.
> FIELD
> Seq. No. | Field Name | Type | Max. Width
> --- | --- | --- | ---
> | starting date | D | 8
> | hour | N | 2
> | ending time | T | 4
> | total msg transmission threshold exceptions | N | 7
> | total msg transmission limit exceptions | N | 7
> | remote deliveries rescheduled | N | 8
> | maximum simultaneous channels | N | 3
> | total incoming calls unanswered | N | 5
> | total remote undeliverable messages | N | 8
> | network channel 1 type | C | 6
> | network channel 1 usage, incoming | N | 7
> | network channel 1 usage, outgoing | N | 7
> | network channel 1 usage, total | N | 7
> | network channel 1 peg count, incoming | N | 6
> | network channel 1 peg count, outgoing | N | 6
> | network channel 1 peg count, total | N | 6
> | network channel 2 type | C | 6
> | network channel 2 usage, incoming | N | 7
> | network channel 2 usage, outgoing | N | 7
> | network channel 2 usage, total | N | 7
> | network channel 2 peg count, incoming | N | 6
> | network channel 2 peg count, outgoing | N | 6
> | network channel 2 peg count, total | N | 6
> | network channel 3 type | C | 6
> | network channel 3 usage, incoming | N | 7
> | network channel 3 usage, outgoing | N | 7
> | network channel 3 usage, total | N | 7
> | network channel 3 peg count, incoming | N | 6
> | network channel 3 peg count, outgoing | N | 6
> | network channel 3 peg count, total | N | 6
> | network channel 4 type | C | 6
> | network channel 4 usage, incoming | N | 7
> | network channel 4 usage, outgoing | N | 7
> | network channel 4 usage, total | N | 7
> | network channel 4 peg count, incoming | N | 6
> | network channel 4 peg count, outgoing | N | 6
> | network channel 4 peg count, total | N | 6
> | network channel 5 type | C | 6
> | network channel 5 usage, incoming | N | 7
> | network channel 5 usage, outgoing | N | 7
> | network channel 5 usage, total | N | 7
> | network channel 5 peg count, incoming | N | 6
> | network channel 5 peg count, outgoing | N | 6
> | network channel 5 peg count, total | N | 6
> | network channel 6 type | C | 6
> | network channel 6 usage, incoming | N | 7
> | network channel 6 usage, outgoing | N | 7
> | network channel 6 usage, total | N | 7
> | network channel 6 peg count, incoming | N | 6
> | network channel 6 peg count, outgoing | N | 6
> | network channel 6 peg count, total | N | 6
> | network channel 7 type | C | 6
> | network channel 7 usage, incoming | N | 7
> | network channel 7 usage, outgoing | N | 7
> | network channel 7 usage, total | N | 7
> | network channel 7 peg count, incoming | N | 6
> | network channel 7 peg count, outgoing | N | 6
> | network channel 7 peg count, total | N | 6
> | network channel 8 type | C | 6
> | network channel 8 usage, incoming | N | 7
> | network channel 8 usage, outgoing | N | 7
> | network channel 8 usage, total | N | 7
> | network channel 8 peg count, incoming | N | 6
> | network channel 8 peg count, outgoing | N | 6
> | network channel 8 peg count, total | N | 6
> | network channel 9 type | C | 6
> | network channel 9 usage, incoming | N | 7
> | network channel 9 usage, outgoing | N | 7
> | network channel 9 usage, total | N | 7
> | network channel 9 peg count, incoming | N | 6
> | network channel 9 peg count, outgoing | N | 6
> | network channel 9 peg count, total | N | 6
> | network channel 10 type | C | 6
> | network channel 10 usage, incoming | N | 7
> | network channel 10 usage, outgoing | N | 7
> | network channel 10 usage, total | N | 7
> | network channel 10 peg count, incoming | N | 6
> | network channel 10 peg count, outgoing | N | 6
> | network channel 10 peg count, total | N | 6
> | network channel 11 type | C | 6
> | network channel 11 usage, incoming | N | 7
> | network channel 11 usage, outgoing | N | 7
> | network channel 11 usage, total | N | 7
> | network channel 11 peg count, incoming | N | 6
> | network channel 11 peg count, outgoing | N | 6
> | network channel 11 peg count, total | N | 6
> | network channel 12 type | C | 6
> | network channel 12 usage, incoming | N | 7
> | network channel 12 usage, outgoing | N | 7
> | network channel 12 usage, total | N | 7
> | network channel 12 peg count, incoming | N | 6
> | network channel 12 peg count, outgoing | N | 6
> | network channel 12 peg count, total | N | 6
> #### Example The following command retrieves the traffic : network load : day screen data for May 22, 2001, displays a transfer statistics summary, and writes output to a file named daylds. getnet -r r1v8 -f day -d 052201 -v > daylds <RETURN> The following data is written to the file: `19940522,2359,0,0,19,3,1,4494,167,0,0,0,70,514,4583, 162,7,0,0,0,10,30,171,0,4494,237,514,4583,162,17,30, 171,0,0,0,0,0,0,0,0,0,0,0,0 <RETURN>` ### getperf Get performance data #### Syntax
> getperf [-d] [-f] [-D mmddyy] [-t hh] [-n nn][-r release] [-N] [-v] [-w] [-V] [>ofile]
> #### Description This command retrieves the INTUITY AUDIX System performance data. Retrieved data is written to standard output.
> -D | Date flag; must be followed by mmddyy.
> mmddyy | Retrieves data for the month day and year indicated by mmddyy.
> -t | Hour flag; must be followed by hh.
> hh | Retrieves data starting on the hour specified by hh on the date you specified by -D mmddyy. The default is 0.
> -n | Hours of data flag; must be followed by nn.
> nn | Retrieves the number of hours of data specified by nn starting on the hour specified by -h hh on the date you specified by -D mmddyy. You also may specify all to get all the hours on and after the date and time specified. The default is 1.
> -r | Release flag; must be followed by release.
> release | Retrieves data for the specified release of the software.
> -v | Writes transfer statistics to the screen at the end of the transfer.
> | Pressing v while the command is executing sends the updated transfer status to the screen.
> -w | Writes a one-line summary of the exit status of this command into the file, getperf.rc.
> -V | Writes the ADAP version number for this command and exits without transferring any screens data.
> > ofile | Specifies the name of the file to which data is written. The filename must be preceded by the symbol >. If no output file is specified, data is written to the screen.
Note: During a system reboot, performance data is reset. #### Output format Output for the performance data is formatted as follows: Each peg, statistic, and histogram and INTUITY AUDIX System processor occupancy record contains: `"label", "type", data value, data value, . . .` Note: The getperf command only supports the default delimter of double quote (`"`) and will not recognize the environment variable named DLIM if DLIM is set to a character other than double quote. #### General Information In the INTUITY Systems, hourly performance data is kept for the previous 8 days. #### Example The following command retrieves the INTUITY AUDIX Systems' performance data for February 26, 2001, and writes output to a file named perfdata. getperf -D 022601 -r l-r6.0 > perfdata <RETURN> #### Data Types The getperf command collects the following types of data: Peg counts Statistics and histograms Processor occupancy LAN Traffic Entering a single getperf command retrieves all types of data. #### Performance data to be collected This section defines the data that is collected. Pegs The peg counts have a type PEG and have a single data value. On an INTUITY or AUDIX System, peg counts are created and saved on an hourly basis, then reset for the next hour. Each peg count is described below with the data label in parentheses: Guest Connections (PF_GUEST_CONNECT_PEG) is the number of successful guest logins. Leave Word Calling Connections (PF_LWC_CONNECT_PEG) is the number of leave word calling messages created. Entry of *H (PF_HELP_PEG) is the number of times *H is used. Entry of *W (PF_WAIT_PEG) is the number of times *W (wait) is used. Tokens (PF_TOKEN_PEG) is the number of touch tone commands correctly entered. Dial Ahead Tokens (PF_DA_TOKEN_PEG) is the number of touch tone commands correctly entered before the announcement requesting the command begins to play. (The next eight pegs are the number of times each is entered on the main activity menu:) Create Outgoing Mail (PF_COMM_ACT_PEG) Scan Incoming Mail (PF_SIM_ACT_PEG) Greeting Administration (PF_GA_ACT_PEG) Scan Outgoing Mailbox (PF_SOM_ACT_PEG) Subscriber Administration (PF_SA_ACT_PEG) Outcalling Administration (PF_OC_ACT_PEG) Automatic Message Scan (PF_AMS_ACT_PEG) System Administration (PF_SY_ACT_PEG) Address Entered By Extension (PF_EXT_ADDR_PEG) is the number of times a message is addressed using the subscriber's extension. Address Entered By Name (PF_NAME_ADDR_PEG) is the number of times a message is addressed using the subscriber's name. Addresses Entered By List (PF_LIST_ADDR_PEG) is the number of times a list is used to address a message. Categories Skipped (PF_SKIPCAT_PEG) is the number of times *# is entered to skip to the next category. Messages Forwarded (PF_FWD_PEG) is the number of times 12 or 13 is entered to forward an incoming message. Messages Replied To By Voice Mail (PF_VM_REPLY_PEG) is the number of times 11 is entered to reply to a message. Messages Replied To By Calling Sender (PF_XFER_REPLY_PEG) is the number of times 10 is entered to call the sender of an incoming message. Lists Created (PF_CREATE_LIST_PEG) is the number of times a 1 is entered to create a list. Deltas Sent (PF_ND_SENT_PEG) is the number of networking deltas (administrative updates) sent to another AUDIX System. Deltas Received (PF_ND_RECD_PEG) is the number of networking deltas (administrative updates) received from another AUDIX System. Full Mailbox (PF_FMBOX_PEG) is a count of all call answer sessions where the subscriber's mailbox is full. File Cabinet (PF_FILE_CAB_PEG) is a count of messages stored in the file cabinet. Messages sent (PF_RM_SENT_PEG) is a count of networked messages sent. Messages received (PF_RM_RECD_PEG) is a count of networked messages received. Subscribers sent (PF_SBS_SENT_PEG) is the number of subscribers sent during full update sessions. Subscribers received (PF_SBS_RECD_PEG) is the number of subscribers received during full update sessions. Remote names (PF_VS_SENT_PEG) is the number of remote names sent.. Remote names (PF_VS_RECD_PEG) is the number of remote names received. Message transmissions (PF_XMT_SENT_PEG) is a count of message transmissions to remote systems. Message transmissions (PF_XMT_RECD_PEG) is a count of message transmissions from remote systems. Statistics and Histograms There are two types of statistics and two types of histograms included in the performance data. INTUITY uses PUDSTAT and PTSTAT, but both are simply represented by STAT. The data for both of these types is identical and is in the following format: INTUITY AUDIX Systems: `"`label`"`,`"`type`"`,min,max,pegs,total,sum-of-squares The average value is equal to total divided by pegs. All five values are initialized to zero each hour on a INTUITY AUDIX System. The average for a particular interval of time can be determined by reading the data at the beginning and at the end of the interval and taking the difference of the pegs and total values before dividing. Min indicates the minimum value and max indicates the maximum value during the interval of time. INTUITY uses PONESECOND and PDBLBLANK, but both are simply represented by HIST. The data for histograms are basically a set of numbers, one of which is incremented each time an event occurs. The number that is incremented depends on the value of the particular event. For INTUITY AUDIX Systems, each histogram includes two additional numbers: the first number represents underflow (values less than those in the smallest cell), the last number represents overflow (values greater than those in the largest cell). The INTUITY AUDIX System uses the following format: `"label","PONESECOND",underflow(unused),0-1,1-2,...,8-9,9-10,overflow (>10)` The data is initialized to zero at the beginning of each hour on INTUITY and AUDIX System each is incremented continuously. Processor Occupancy Processor occupancy data measures the average occupancy over a five minute interval. For the Feature Processor (FP), Voice Session Processor (VSP), and the Data Base Processor (DBP), 24 hours of occupancy data is available for the 24 hours before that data is retrieved. For the Multi-Function Board (MFB) and for the INTUITY AUDIX system, eight days of occupancy data are available just as they are for all other performance statistics. The type for all occupancy measurements is `"`CPU_DATA`"`. The labels for the occupancy measurements are `"`FP_OCCUPANCY`"`, `"`VSP_OCCUPANCY`"`, and `"`DBP_OCCUPANCY`"` and `"`CPU_OCCUPANCY`"` for INTUITY. For the FP, VSP, and DBP, each line contains one hour's worth of data beginning at the date and time shown. Therefore, there are a total of 24 lines of data for the FP, VSP, and DBP. For INTUITY AUDIX System, each line contains one hour's worth of data beginning at the date and time shown; there is one line for every hour requested. ADAP collects the following CPU_OCCUPANCY data for an INTUITY system: (IDLE_DATA) system idle time (percent) (CPU_DATA) sum of user and system CPU occupancy (percent) (WIO_DATA) wait I/O time (percent) (PAGE_SCAN) page scans per second (KERNEL_MEM) dynamic kernel memory allocated (MB/hour) The system registers an event in the event log whenever one of the above measurements is outside the recommended range. In addition, a warning alarm is generated whenever the system idle time is too low (less than 10% for 20 minutes or more during the last hour). The only other data that appear in the output file for a INTUITY AUDIX System after using the getperf command is one line indicating the date and time of day associated with the data. LAN Traffic Data The following data is collected about the LAN traffic on the INTUITY system: (LAN_DATA, PKTS_SENT) number of packets sent by the INTUITY system to the LAN interface since the INTUITY was last booted (LAN_DATA, PKTS_RCVD) number of packets received by the INTUITY system from the LAN interface since the INTUITY was last booted (LAN_DATA, BYTES_SENT) number of bytes sent by the INTUITY system to the LAN interface since the INTUITY was last booted (LAN_DATA, BYTES_RCV) number of bytes received by the INTUITY system from the LAN interface since the INTUITY was last booted (LAN_DATA, PKTS_RXMT) number of packets retransmitted from the INTUITY system to the LAN interface since the INTUITY was last booted #### Data collection For the INTUITY AUDIX Systems, the getperf command writes the time associated with the data to be retrieved. It then issues an appropriate number of commands to retrieve the performance file for the date and times specified. #### Output format for each data type The following list provides an example for each type of performance data: Pegs `"`PF_GUEST_CONNECT_PEG`"`,`"`PEG`"`,5 Statistics `"`PF_CLMS_STATS`"`,`"`PUDSTAT`"`,17,1,45,269,0 Histograms `"`PF_RCP_HIST`"`,`"`PDBLBLANK`"`,590,102,20,3,7,10,3,2,6,9,2,0,0,0,0,0,0, 0,0,0 MFB Occupancy `"`MFB_OCCUPANCY`"`,`"`CPU_DATA`"`,24.1,19.4,18.9,15.9,22.3,26.2,13.0, 14.72,16.4,10.8,11.3 FP/VSP Occupancy `"`FP_OCCUPANCY`"`,`"`CPU_DATA`"`,19890809,1700,39.0,36.0,33.0,28.7, 26.2, 29.6,26.2, 20.2,etc. DBP Occupancy `"`DBP_OCCUPANCY`"`,`"`CPU_DATA`"`,19940809,1730,50.6,31.0,47.5,36.5, 53.7,49.8,48.2,41.2,38.0,37.3,51.0,49.4 CPU Occupancy for the INTUITY AUDIX System `"`CPU_OCCUPANCY`"`,`"`CPU_DATA`"`,52,46,51,47,51,47,59,50,51,51, 50,49 Top of page

| Search This CD Index Contact Us
| © 2002-2007 Avaya Inc. All rights reserved.